-
-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce JEP for External Fingerprint Storage #289
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good as a JEP draft, thanks! The format is followed.
I will merge it in 24 hours if there is no negative feedback at the Cloud Native SIG meeting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments; mostly small legibility updates
jep/0000/README.adoc
Outdated
|
||
When a plugin is configured and enabled, the fingerprints are transferred from the local storage to the external storage. | ||
|
||
This by followed by clearing the local database of fingerprints from Jenkins HOME ONLY if the writes are successful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is followed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jep/0000/README.adoc
Outdated
|
||
We do not propose to revamp the `FingerprintCleanupThread` to use the above logic at the moment. | ||
|
||
==== External to Local Migration (Nice 2 Have) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change "nice 2 have"s to "out of scope for MVP" ... or at the very least, s/2/to/ ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably actually move these sections to the bottom so they don't distract from the important stuff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@afalko thanks! Incorporated "out of scope for MVP" :)
I have these at the end of the Design Decisions section
I will go ahead and merge it
…On Fri, Jun 12, 2020, 17:07 Andrey Falko ***@***.***> wrote:
***@***.**** approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#289 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW4RIEQTKMLYRMWKDBSIWDRWJAD7ANCNFSM4N2ULHCA>
.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Structure of JEP looks good to me and writing is clear. The (out of scope for MVP) sections could perhaps be moved to Reasoning (i.e., why they are out of scope), but I think it is also OK under Specification as you are just noting in which phase something might be implemented.
Co-authored-by: Jesse Glick <[email protected]>
JEP-225 ID is locked by #266. It does not really follow the JEP process, but I do not want to provoke additional merge conflicts. We are not required to do sequential numbering. I will merge one as JEP-226. |
@@ -1,4 +1,4 @@ | |||
= JEP-0000: External Fingerprint Storage | |||
= JEP-226: External Fingerprint Storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@oleg-nenashev will you update https://www.jenkins.io/sigs/cloud-native/pluggable-storage/ to match?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing it out @jglick, Ill submit a PR to update it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Somebody will do it, if course.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CC @oleg-nenashev @afalko @mikecirioli